-
Notifications
You must be signed in to change notification settings - Fork 360
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adjusted dockerfile so that build args can be provided to switch the … #8420
adjusted dockerfile so that build args can be provided to switch the … #8420
Conversation
…build from musl-amd64 to amd64
Donlan, Christopher seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
I've signed the CLA. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, this contribution will be great for our more advanced users! I want to pull this, of course.
-
Your CLA is still showing red. This unfortunately happens occasionally. Can you attach a link to somewhere on the CLA Assistant website that shows you have signed it? I am really sorry about this hassle, but this is an unfortunate fact of life with OSS-licensed code.
I will try to see whether I can kick it into motion in some way on my side.
-
I ran Esti (integration tests) on this PR, all is green.
-
So other than virtual paperwork, I think we're good to go!
I made some changes...will come back to this likely tmrw. |
@arielshaqed updated w/ CLA screen shot. I've given the CLA access to my account, officially, and see it in my doc table. |
Thanks, @chrisdonlan ! I'm ensuring that we're allowed to replace CLA Assistant with common sense, and will pull if I can or update if we need more help. Really sorry about having to drag this. |
Okay! Thanks for providing all information about the CLA, I can pull as soon as tests pass. Should be ready soon. |
PULLING, thanks! @chrisdonlan you can of course use this immediately with no need to wait for a release - the Dockerfile changes are not a part of any release artefact, and indeed should not change any of our release artefacts. |
Closes #8419
Change Description
I added the following build args to generalize the
Dockerfile
todebian::bookworm
.BUILD_REPO
BUILD_TAG
BUILD_PACKAGES
IMAGE_REPO
IMAGE_TAG
IMAGE_PACKAGES
ADD_PACKAGES
Background
I mentioned this in LakeFS' help channel in slack, and was recommended to create this issue and make a PR. This is no problem, and I went ahead and generalized the
Dockerfile
so that we can toggle our base repo, architecture, and so on via our CI/CD build variables.Bug Fix
If this PR is a bug fix, please let us know about:
New Feature
The base docker image can now be built with an arbitrary linux base image, e.g.
debian:bookworm
:Testing Details
I built the image.
Breaking Change?
It doesn't break anything, per say. However, I ran into a bug that I saw on both the unchanged
master
branch and my updated branch. Namely, I saw the following go error when building on anarm64
mac w/colima
inx86_64
emulation mode viaqemu
:I assume this is because of my setup, and I hope that we'll still be able to build the image in our CI/CD.
Additional info
Contact Details
[email protected]